feat(ui): add reusable developer surface system - #3

Objective

Evolve OpenCoven UI from a component specimen library into a reusable development-surface system for project context, SDK/CLI integration state, daemon/runtime authority cues, and verifiable execution receipts—without turning this repository into another runtime or product authority.

This PR is stacked on #2, which is stacked on #1. It should merge after both foundations.

Architecture

The integration boundary follows current OpenCoven ownership:

• @opencoven/sdk is represented as an experimental, read-only data source; UI does not imply deferred mutation APIs exist.
• @opencoven/cli / coven is the canonical user-facing CLI; the SDK repository’s private @opencoven/dev-cli is not presented as public product surface.
• Coven remains daemon/session/runtime authority.
• Threads, Psyche, and Coven remain canonical producers of protected mutation and orchestration state.
• Cave remains production application/UI behavior authority.
• @opencoven/ui accepts normalized view models and renders state; it performs no discovery, credential access, transport negotiation, or mutation.

What changed

• adds ConnectionStatus for SDK/CLI/daemon/runtime/project health plus explicit authority level
• adds CommandReceipt for pre-redacted CLI/SDK/daemon/runtime invocation evidence
• adds DeveloperSurface, a responsive assembled block combining project context, integrations, receipts, and adapter guidance
• exports all three from the package and package subpaths
• adds an isolated /developer reference surface showing the canonical CLI, experimental read-only SDK, daemon authority, and coven-code runtime state
• applies persisted scheme and density before rendering every specimen route, including /developer
• removes fake or no-op controls so affordances never imply an operation the host cannot perform
• makes the developer surface, connection cards, command evidence, navigation, metadata, and install commands reflow safely at narrow widths and 200% text
• adds accessibility/unit coverage for textual state, invocation evidence, assembled semantics, stable identity, and axe
• adds docs/developer-surface.md with the SDK/CLI adapter, authority, receipt, and protected-data contracts
• adds a dedicated shadcn registry fragment for all three public items
• expands the clean-consumer test to install and type-check developer-surface from generated registry output
• makes deployment generate registry output before the specimen build so /r/* cannot silently lag source
• checks untracked generated registry files as well as tracked drift
• adds architecture contracts preventing UI-package dependencies on SDK/CLI runtimes and enforcing the presentation-only boundary
• adds dedicated /developer desktop, mobile, light/dark, compact, and 200%-text visual receipts

Deliberate non-goals

• no dependency on @opencoven/sdk or @opencoven/cli
• no runtime I/O inside UI components
• no new authority semantics
• no production Cave behavior changes
• no claim that the experimental SDK is mutation-ready
• no replacement for product-specific Cave integration testing

Verification

Final head: 713e305ad6a515dd3ba31e7bf697685a54ddd5eb

• GitHub CI — success
• GitHub Visual review — success
• canonical opencoven-ui Vercel preview — Ready
• PR mergeability — clean
• all three inline review threads — resolved
• final intended delta — 24 files, with no transient helper workflows or staging files

Ordinary CI verifies:

• repository formatting and lint
• workspace type checking
• 4 test files / 15 tests, including accessibility checks
• architecture and design contracts
• 36-item registry composition, validation, and deterministic output
• clean consumer installation of Composer and Developer Surface
• package and specimen production builds
• deploy-output verification
• packed-package verification

Visual receipts verify:

• Library and Assembled surfaces across desktop/mobile, light/dark, and cozy/compact modes
• /developer dark desktop
• /developer dark mobile at 390px compact
• /developer light desktop compact
• /developer dark mobile at 390px and 200% text
• four connection sources and three command receipts render without duplicate IDs, fake controls, internal clipping, or document overflow
• the entire 320/375/390/430px mobile matrix, RTL, reduced motion, and 390px at 200% text remains green

At 390px and 200% text, document, card, stage, tab-root, transcript, session-header, and developer-surface overflow are all zero.

Public additions

• ConnectionStatus
• CommandReceipt
• DeveloperSurface
• /developer reference surface
• registry items:
  • connection-status
  • command-receipt
  • developer-surface

Risk and rollback

The components remain presentation-only and accept bounded host-owned view models. They introduce no SDK/CLI runtime dependency and perform no authority-bearing operation. Revert this PR to remove the developer-surface system without affecting the specimen-shell or visual-receipt foundations.